Check category: Availability

Check description: Validate that the node ID values between LLT and Oracle Clusterware are the same.

Check procedure:

• Retrieves the node ID values from the llthosts file.

Check recommendation: It is recommended that the node ID values between Low Latency Transport (LLT) and Oracle Clusterware should be same.

Check category: Availability

Check description: Checks if the GAB_START entry in the GAB configuration file is set to 1.

Check procedure:

• Verifies whether the GAB_START entry in the GAB configuration file is set to 0.

Check recommendation: Make sure that the GAB_START entry in the GAB configuration file is set to 1 so that the GAB module is enabled and ready to startup after system reboot.

Check category: Availability

Check description: Checks if any of the private links in the cluster are in the jeopardy state.

Check procedure:

• Checks the network connectivity of the target host with the other hosts in the cluster.

Check recommendation: 1. Determine the connectivity of this node with the remaining nodes in the cluster. Enter:
/sbin/lltstat -nvv
If the status is DOWN this node cannot see that link to the other node(s).
2. Restore connectivity through this private link.
3. Verify that connectivity has been restored. Enter:
# /sbin/gabconfig -a | /bin/grep jeopardy
If this command does not have any output, the link has been restored.

Check category: Availability

Check description: Checks whether all GAB ports are configured on the system.

Check procedure:

• Identifies all the GAB ports that are configured on the system.

Check recommendation: It is recommended that you configure all the GAB ports in the system.

Check category: Availability

Check description: Verifies whether I/O fencing is properly configured for cluster.

Check procedure:

• Determines the fencing mode using the 'vxfenadm' command and verifies whether fencing mode is set to either SCSI-3 or SYBASE or CPS or customized.

Check recommendation: Either I/O fencing is not running on the system or fencing mode is not configured properly. It is recommended to configure I/O fencing with fencing mode configured as per product requirements when using SFCFS to avoid VxFS file system corruption.

Check category: Availability

Check description: Checks that packages installed across all the nodes in a cluster are consistent

Check procedure:

• Identifies the packages installed on all the nodess in a cluster.

Check recommendation: Ensure that packages installed on all the nodes in a cluster are consistent and package versions are identical. Inconsistent packages can cause errors in application fail-over.

Check category: Availability

Check description: Checks whether the processors have the same clock cycle frequency across the cluster.

Check procedure:

• Determines the CPU speed of each system in the SFRAC cluster.

Check recommendation: All nodes in a cluster must have identical processors with the same clock cycle frequency.

Check category: Best practices

Check description: Checks whether the installed Storage Foundation / InfoScale products are at the latest software patch level.

Check procedure:

• Identifies all the Storage Foundation / InfoScale products installed on the system.

Check recommendation: To avoid known risks or issues, it is recommended that you install the latest versions of the Storage Foundation / InfoScale products on the system.